Keep Active Agents in its VS Code container#429
Merged
Conversation
VS Code rejects activity bar container identifiers that contain dots, which caused the Active Agents contribution to fall back into Explorer and left the focus command targeting a container that was never registered. The live and template manifests now use a hyphenated container id while the existing view id stays unchanged. Constraint: VS Code view container ids allow only alphanumeric characters, underscore, and hyphen Rejected: Rename the gitguardex.activeAgents view id | wider command/menu/test churn was unnecessary Confidence: high Scope-risk: narrow Directive: Keep live and template Active Agents manifests and focus commands in sync when changing VS Code contribution ids Tested: node --test test/vscode-active-agents-session-state.test.js Tested: npm test Tested: node scripts/install-vscode-active-agents-extension.js
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated by gx branch finish (PR flow).